Description

This pull request implements pagination for the getAllBillingPlans endpoint. It adds page and limit query parameters to the endpoint, allowing clients to retrieve billing plans in smaller chunks, improving performance and scalability.

Related Issue

Type of Change

• Added Pagination Feature

How Has This Been Tested?

• Unit tests

Test Evidence

Documentation Screenshots (if applicable)

Checklist

• My code follows the project's coding style
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published
• I have included a screenshot showing all tests passing
• I have included documentation screenshots (if applicable)

Additional Notes

• Database Configuration Issues: I encountered significant difficulties setting up the local database connection. I tried [list the things you tried, e.g., different connection strings, different users, different migration strategies], but I was unable to get it working correctly.

• Mock Data Source: To overcome this issue and demonstrate the pagination functionality, I implemented a mock data source in the BillingPlanService. This allows the API to return paginated results without relying on the database.
  Then did a test to confirm feature was working then removed the mock data

• Assumptions: This implementation assumes that the database connection will be properly configured in a production environment. The pagination logic should function correctly once the database connection is established.
  -I have tried my best in doing the task and have asked questions whenever problems arise.